docs: align API stability guarantees with 1.0.0 release (#597)#629
Merged
Craigacp merged 2 commits intotensorflow:masterfrom Jan 20, 2026
Merged
docs: align API stability guarantees with 1.0.0 release (#597)#629Craigacp merged 2 commits intotensorflow:masterfrom
Craigacp merged 2 commits intotensorflow:masterfrom
Conversation
mihaimaruseac
left a comment
mihaimaruseac
left a comment
There was a problem hiding this comment.
This seems in alignment with #597 but project maintainers should be the ones approving.
Collaborator
|
Please run spotless to fix the formatting, then we can merge it. |
Contributor
Author
|
Hi @Craigacp — I have updated the PR to resolve the formatting violations. The "spotless:check" is now passing. |
Craigacp
approved these changes
Jan 20, 2026
Collaborator
|
Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This Pull Request resolves the contradictions pointed out in issue #597 regarding the API stability status of the TensorFlow Java project.
While the 1.0.0 release notes officially committed the project to the TensorFlow API stability guarantees, several key documentation files (install.md and package-info.java) still contained "Experimental" warnings and disclaimers. These legacy warnings often discourage production adoption and conflict with the project's current maturity level.
Changes Made
Technical Nuance
As discussed in the issue thread, this PR does not offer a "blanket" guarantee that ignores the realities of the underlying C++ core. Instead, it shifts the narrative from "Experimental/Unstable" to "Stable with Upstream Dependencies," which accurately reflects the architecture of the Java bindings.
CC: @Craigacp @karllessard @mihaimaruseac Note: I've updated the wording to find a middle ground between the 1.0.0 release guarantees and the upstream dependency concerns discussed in #597.
Related Issues
Fixes #597